home *** CD-ROM | disk | FTP | other *** search
- Path: fido.asd.sgi.com!austern
- From: David Byrden <100101.2547@compuserve.com>
- Newsgroups: comp.std.c++
- Subject: Can Allocators be used outside of RAM?
- Date: 22 Jan 1996 09:39:26 PST
- Organization: self-employed
- Approved: austern@isolde.mti.sgi.com
- Message-ID: <4drn5s$8n9@news.bridge.net>
- NNTP-Posting-Host: isolde.mti.sgi.com
- X-Original-Date: 20 Jan 1996 21:34:52 GMT
- X-Mailer: Mozilla 1.1N (Windows; I; 16bit)
- X-Auth: PGPMoose V1.1 PGP comp.std.c++
- iQBVAwUBMQPL4Ey4NqrwXLNJAQFuJQH/X6qdkWis8DkjtUGK2jX+bp0x33ICyyme
- KRFFTAgQcmLxo0PPTyujJfD3OvQZGOh2Gp7Kc4pm3S1KT1VklWtDxQ==
- =RG66
- Originator: austern@isolde.mti.sgi.com
-
- I wonder whether anyone can clarify one intent of the Standards
- committee with respect to allocators?
-
- I hope that it shall be possible, through provision of an Allocator
- class, for containers to use generalised storage devices for their
- data; for example, devices accessed through an API.
-
- Reading the September '95 draft standard, however, I find mention only of
- "main memory, shared memory, or private heaps" and the recent
- requirements that allocator-supplied pointers and references be
- convertible to T* and T&. These seem to suggest that allocators can only
- support addressable memory.
-
- I cannot deduce unambigously from the various specifications whether API
- storage is or is not intended to be usable through Allocators. Does
- anyone know?
-
-
- David
- ---
- [ comp.std.c++ is moderated. Submission address: std-c++@ncar.ucar.edu.
- Contact address: std-c++-request@ncar.ucar.edu. The moderation policy
- is summarized in http://dogbert.lbl.gov/~matt/std-c++/policy.html. ]
-